Plan timetable

There is a problem

27 ‘plan’ fields do not match the ‘reference’ field in the plan dataset

entity: 5110094

reference: wbc-local-plan-gateway-2-advice-sought
plan: undefined
waverley-borough-council-local-plan-2026
plan-event: gateway-2-advice-sought
event-date: 2027-10-18
actual-date
entry-date: 2026-06-11
notes: We will seek observations and advice from the Planning Inspectorate (PINS) to help identify and resolve potential soundness issues at an early stage, and to ensure the plan is progressing towards meeting the statutory and policy requirements set out in legislation and national planning policy.

How to fix this issue

Your data is missing a plan.

The plan timetable guidance explains how to fix the issue:

plan

This is the unique reference for your overall plan. For example:

LP-BRX-2024
barnet-local-plan-2021-2036
hertfordshire-minerals-and-waste-plan
essex-minerals-plan
essex-waste-plan
county-durham-supplementary-plan

The ‘plan’ field in your plan timetable dataset must match the ‘reference’ field from your plan dataset.

This diagram shows the relationship between the plan dataset and the plan timetable dataset. The reference value from your plan dataset needs to match the plan value in your plan timetable dataset. This is so that we can match your timetable to the right plan.

How to improve Waverley Borough Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL